Columbia Kermit/kermit.zip/newsgroups/misc.19960715-19961006/[e-mail] _Fri Aug 9 14:15:05 1996.msg

Internet Message Format | 2020-01-01 | 4KB

Return-Path: [e-mail]
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30]) by watsun.cc.columbia.edu (8.7.5/8.7.3) with ESMTP id OAA05331 for <[e-mail]>; Fri, 9 Aug 1996 14:15:04 -0400 (EDT)
Received: (from news@localhost) by newsmaster.cc.columbia.edu (8.7.5/8.7.3) id OAA10803 for kermit.misc@watsun; Fri, 9 Aug 1996 14:15:01 -0400 (EDT)
Path: news.columbia.edu!panix!newsfeed.internetmci.com!usenet.eel.ufl.edu!warwick!bham!B.A.McCauley
From: [e-mail]
Newsgroups: comp.protocols.kermit.misc
Subject: Re: MS-KERMIT 3.14 server "REMOTE DELETE" problem
Date: 09 Aug 1996 16:32:44 GMT
Organization: The University of Birmingham, UK.
Lines: 63
Message-ID: <[e-mail]>
References: <[e-mail]>
    <4ucor3$[e-mail]>
NNTP-Posting-Host: wcl-l.bham.ac.uk
To: [e-mail] (Frank da Cruz)
In-reply-to: [e-mail]'s message of 8 Aug 1996 13:07:47 GMT

In article <4ucor3$[e-mail]>,
 [e-mail] (Frank da Cruz) writes:
>In article <[e-mail]>,
> <[e-mail]> wrote:
>: I have a PC running MS-KERMIT 3.14 server to provide access to a
>: filesystem.  The application talking to this server is a home-grown
>: implementation of the Kermit protocols.  When the application attempts
>: to delete a file using the "REMOTE DELETE" command I get a problem if
>: any of the components of the filename start with a digit.  I assume
>: this is because the backslash-digit sequence is being interpreted as a
>: control character.
>:
>Perhaps, but by whom?

Well it's not my software and I very much doubt it's COMMAND.COM this
leaves MS-KERMIT as the prime suspect.

>When sending a server command from C-Kermit or MS-DOS Kermit to a Kermit
>server that runs on a DOS-like file system, you have to double the
>backslashes in your commands, to force the *command interpreter* to take
>the backslash literally.

Oh no you don't!  The *DOS* command interpreter does not treat
backlashes as special.  Unix ones do.  It still seems odd to me that
using the "*GENERIC* delete" command that the protocol would allow me
to be affected by idiosyncracies of the host operating system's
command interpreter.

>In the Kermit *protocol*, there is nothing special about backslashes.
>Here are the packets from a successful REMOTE DELETE operation:
>
>  ^A1 GE,c:\tmp\123.xT
>  ^A3 Ydel c:\tmp\123.xL
>
>As you can see, the backslashes are backslashes.

Here are the packets from an unsuccessful REMOTE DELETE operation:

  ^A- GE(T:\123.xG
  ^A, Ydel T:{.xK

As you can see, the backslashes are not backslashes once MS-KERMIT has
had it's way with them.

Assuming the packets you showed me are for real, you are telling me by
implication that I have found a bug in MS-KERMIT 3.14pl0 but that it's
already fixed in the version you are using.

In case you are wondering why I'm using pl0 rather than the latest
patch level it's because I had some other problems with ARP in later
versions.  Indeed the problem appeared in exactly the patch level
where the release notes said that an ARP bug had been fixed.  In fact
I've still having ARP problems so I think I'll try upgrading again.

If the backslash bug is still in the later version I'll get back to you.

--
    \\   ( )   No Bullshit!   | Email: [e-mail]
 .  _\\__[oo       from       | Phones: [phone] (home)
.__/  \\ /\@  /~)  /~[   /\/[ |   [phone] (voice) 2175 (fax)
.  l___\\    /~~) /~~[  /   [ | PGP-fp: D7 03 2A 4B D8 3A 05 37...
 # ll  l\\  ~~~~ ~   ~ ~    ~ | http://wcl-l.bham.ac.uk/~bam/
###LL  LL\\ (Brian McCauley)  | Finger: [e-mail]